Simulating i/o using multicomputer data processing

ABSTRACT

Methods, systems, and computer program products are included for simulating I/O. An exemplary method includes simulating I/O from a card that includes a magnetic stripe. The method includes receiving, at a first controller, a first token from a first terminal. The first token is communicated from the first controller to at least one backend computing device. The first controller receives, from the at least one backend computing device, a second token generated at the at least one backend computing device. The first controller injects the second token into a second controller. The second controller communicates the second token to the at least one backend system.

PRIORITY

The present application is a continuation of U.S. patent applicationSer. No. 15/155,464, filed May 16, 2016, issued as U.S. Pat. No.9,734,652, entitled “SIMULATING I/O USING MULTICOMPUTER DATAPROCESSING,” which is herein incorporated by reference in its entirety.

BACKGROUND Field of the Invention

The present disclosure generally relates to electrical computers anddigital data processing systems.

Related Art

Conventional input/output (I/O) devices include devices such as magneticstripe cards, smart/chip cards, smart phones, keyboards, magnetic stripereaders, and chip readers. Traditionally, a magnetic stripe reader readsdata from a magnetic stripe card when a user swipes the magnetic stripealong a magnetic reading head of the magnetic stripe reader. The swipingof the card causes a change in a magnetic field that enables data to beread from the magnetic stripe by the magnetic stripe reader.

Another conventional I/O device is a smart card, or a chip card, whichtypically includes a card that has an embedded microchip, such as an EMVsmart chip. Traditionally, the microchip of the smart card is dippedinto a chip reader or tapped against a chip reader to transmit data to achip reader. The chip reader reads data from the microchip eitherthrough physical contact with the microchip or via a wirelesstechnology, such as an electromagnetic field communication.

Other conventional I/O devices include smart phones and other portableelectronics that may communicate using technologies such as Bluetooth,near-field communication (NFC), and/or other wired and wirelesstechnologies.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention is illustrated by way of example and notlimitation in the figures of the accompanying drawings.

FIG. 1 is a block diagram illustrating a multicomputer systemarchitecture for performing data processing, in accordance with variousexamples of the present disclosure.

FIG. 2 is a block diagram illustrating a multicomputer systemarchitecture for performing data processing, in accordance with variousexamples of the present disclosure.

FIG. 3 is a block diagram illustrating a computer system suitable forimplementing one or more computing devices.

FIG. 4 is a flow diagram illustrating a method for processing atransaction, in accordance with various examples of the presentdisclosure.

DETAILED DESCRIPTION

In the following description, specific details are set forth describingsome embodiments consistent with the present disclosure. It will beapparent, however, to one skilled in the art that some embodiments maybe practiced without some or all of these specific details. The specificembodiments disclosed herein are meant to be illustrative but notlimiting. One skilled in the art may realize other elements that,although not specifically described here, are within the scope and thespirit of this disclosure. In addition, to avoid unnecessary repetition,one or more features shown and described in association with oneembodiment may be incorporated into other embodiments unlessspecifically described otherwise or if the one or more features wouldmake an embodiment non-functional.

Various examples described herein provide a computing device thatreceives an input of a token from a device, such as a smart card or amobile phone. The smart card or mobile phone may generate the token toperform a transaction. The computing device transmits the token to abackend processing system that generates a second token in a format thatwould be provided by a magnetic stripe card. At least a portion of thesecond token includes an identifier that corresponds to the backendprocessing system. The second token is returned to the computing device.The computing device simulates an input of the second token by injectingthe token into a magnetic stripe reader component or a software programrunning on the computing device (or another computing device). Theinjecting of the second token simulates an input of the second tokenfrom a magnetic stripe card. The computing device then processes atransaction using the second token. The transaction includes identifyingthe backend processing system, using the identifier included in thesecond token, and routing the second token to the backend processingsystem.

These techniques are beneficial and advantageous for enabling acomputing device to convert an input from a chip card or a mobile phoneinto a magnetic stripe input. These techniques are useful in a varietyof contexts. For example, in the context of transaction processing,legacy systems may be configured to process transactions using an inputfrom swiping a magnetic stripe or reading a number from a magneticstripe card. These legacy systems may not be compatible withtechnologies such as chip cards and near-field communication.Accordingly, the techniques for simulating a magnetic stripe input areuseful for conversion of I/O (e.g., input, output, or a combinationthereof) from a chip or other format type to a magnetic stripe card I/Otype, such that a transaction may then be performed using the magneticstripe card I/O type. These techniques improve interoperability of acomputing device with smart card and portable electronic technologies,such that the functioning of the computing device is improved. Thesetechniques address particular problems associated with legacy computingdevices and offer solutions that improve the operation of the computingdevices. For example, these techniques allow computing devices toprocess I/O, such as in the context of transaction processing, thatwould otherwise be inaccessible to the computing devices. Of course, itis understood that these features and advantages are shared among thevarious examples herein and that no one feature or advantage is requiredfor any particular embodiment.

FIG. 1 illustrates a multicomputer system architecture 100 forperforming data processing, in accordance with various examples of thepresent disclosure.

System architecture 100 includes a first terminal 102 that is structuredas a computing device. In some examples, the first terminal 102 isstructured to include a magnetic stripe reader that is configured toread data from magnetic stripe cards when the magnetic stripe cards areswiped at the magnetic stripe reader. In other examples, the firstterminal 102 is structured as a keyboard, keypad, and/or other key inputdevice that is structured to accept key press input to accept data thatis read from a magnetic stripe card by a user. For example, a magneticstripe card may include an identifier such as a primary account number(PAN), that may be visually read from the card by a user and typed intothe first terminal 102 via a plurality of key presses.

The first terminal 102 is communicatively coupled to a client computingdevice 104. In some examples, the first terminal 102 is communicativelycoupled to the client computing device 104 via a wired connection (e.g.,a USB cable) or a wireless connection (e.g., Bluetooth).

In the present example, the client computing device 104 is structured asa desktop computer, or other computing device, that includes a firstcontroller 106. The first controller 106 may be structured as, forexample, a computer program comprising one or more instructions that areexecutable to provide an interface to a user. The first controller 106may control the first terminal 102 to perform I/O functions oroperations.

In some examples, the client computing device 104 is located at amerchant point of sale (POS). In this example, the first controller 106may include software, hardware, or a combination thereof that provides apurchasing interface for inputting sales and calculating an amount duefrom a customer. In this example, the first controller 106 is structuredto communicate with the first terminal 102 to request that the firstterminal 102 perform a magnetic stripe I/O operation. For example, thefirst controller 106 may activate the first terminal 102 such that acustomer may swipe a card that includes a magnetic stripe. The firstterminal 102 may then read the data from the magnetic stripe, such as aPAN, and communicate this data to the first controller 106. In otherexamples, these techniques are performed in other contexts such asauthentication, ticketing, user identification, and so forth.

The system architecture 100 includes a token input device 108. In someexamples, the token input device 108 is structured as a smart card/chipcard. In other examples, the token input device 108 is structured as awireless and/or NFC-enabled device, such as a smart phone. The tokeninput device 108 is structured to generate a first token and communicatethe first token to the second terminal 110. Accordingly, in someexamples the second terminal 110 is structured as a chip reader thatreads the first token from the token input device 108 by communicatingwith a microprocessor embedded on the smart card. In other examples, thesecond terminal 110 is structured as a smart phone or other electronicdevice that reads the first token from the token input device 108 via anNFC or other wireless protocol. For example, if the token input device108 is structured as a smart phone or smart card, the token input device108 may be tapped or otherwise moved within a threshold proximity to thesecond terminal 108 to allow the second terminal 108 to read the firsttoken.

In the present example, the client computing device 104 is structured toinclude a second controller 112. While in the present example the firstcontroller 106 and second controller 112 are shown as being structuredon a client computing device 104, in other examples the first controller106 and second controller 112 may be structured on a plurality ofcomputing devices. For example, as shown in FIG. 2, the first controllermay be structured on a first computing device and the second controllermay be structured on a second computing device.

In some examples, the second controller 112 is structured as hardwareand/or software, such as a computer program comprising one or moreinstructions that are executable to provide an interface that controlsthe second terminal 110 to perform I/O. As described above, the clientcomputing device 104 may be located at a POS. The second controller 112may provide an interface for inputting an amount due and/or triggeringthe second terminal 110 to perform I/O functions or operations. In thisexample, the second controller 112 is structured to communicate to thesecond terminal 110 a request that the second terminal 110 read datafrom the token input device 108. For example, the second controller 112may configure and/or activate the second terminal 110 such that acustomer may input a first token from the token input device 108 byinserting a chip card or positioning a smart phone within a thresholdproximity of the second terminal 110. The second terminal 110 isstructured to read the first token from the smart card and/or smartphone and communicate the first token to the second controller 112.

The client computing device 104 is communicatively coupled to a network114. The network 114 may be structured to include a private network,such as an intranet, and/or public network, such as the internet. Theclient computing device 104 is structured to transmit data to and fromthe network 114 to communicate with other computing devices, such as oneor more server computing devices 116.

In the present example, the one or more server computing devices 116 arestructured receive and process data received from the client computingdevice 104 to perform one or more transactions. For example, once thefirst controller 106 receives magnetic stripe data from the firstterminal 102, the first controller 106 may communicate the magneticstripe data to the network 114 via a network card or other networkdevice of the client computing device 104. Similarly, when the secondcontroller 112 receives the first token from the second terminal 110,the second controller 112 may communicate the first token to the network114 via a network card or other network device of the client computingdevice 104. The network 114 communicates the magnetic stripe data orfirst token to the one or more server computing devices 116 forprocessing. In some examples, the processing includes performing atransaction such as transferring funds between a customer account and amerchant account. After performing the transaction, the one or moreserver computing devices 116 may notify the first controller 106 or thesecond controller 112 that the transaction has been processed.

In the present example, the second terminal 110, second controller 112,and/or one or more server computing devices 116 are structured tosimulate magnetic stripe I/O by generating magnetic stripe data andinjecting the magnetic stripe data into the first controller 106. Forexample, this data processing may be performed as described in detailwith respect to FIG. 4. In some examples, the system architecture 100 isstructured to inject magnetic stripe data after the one or more servercomputing devices 116 receive the first token from the client computingdevice 104. For example, the one or more server computing devices 116may generate a second token that represents a PAN or other data thatwould be read from a magnetic stripe. This second token may bestructured to include one or more digits that are uniquely identifiableas associated with the one or more server computing devices 116. The oneor more server computing devices 116 are then structured to communicatethe second token to the second controller 112 at the client computingdevice 104.

In some examples, the second controller 112 is structured to inject thesecond token into the first controller 106 by simulating key inputs totype the PAN or other magnetic stripe data into an interface provided bythe first controller 106. For example, the client computing device 104may be structured with an operating system that includes an applicationprogramming interface (API) that may be called to send key inputs from akeyboard or keypad. In this example, the second controller 112 isstructured to call the API to inject the second token into the firstcontroller 106 via simulated key inputs.

The first controller 106 is structured to perform transaction processingusing the second token. In some examples, the first controller 106 isstructured to transmit the second token to the one or more servercomputing devices 116 to complete the transaction processing. In thepresent example, the second token is routed to the one or more servercomputing devices 116 by the client computing device 104 and/or othertransaction processing systems located on the network 114 based onrecognizing that the second token is associated with the one or moreserver computing devices 116. As previously discussed, the second tokenmay include an identifier that associates the second token with the oneor more server computing devices 116. Accordingly, the one or moreserver computing devices 116 receives the second token as part a of atransaction processing operation, and may be structured to perform oneor more operations, such as transferring funds, sending notifications tothe client computing device 104, and so forth.

FIG. 2 illustrates a multicomputer system architecture 200 forperforming data processing, in accordance with various examples of thepresent disclosure.

System architecture 200 includes a first terminal 202 that is structuredas a computing device. In some examples, the first terminal 202 isstructured to include a magnetic stripe reader that is configured toread data from magnetic stripe cards when the magnetic stripe cards areswiped at the magnetic stripe reader. In other examples, the firstterminal 202 is structured as a keyboard, keypad, and/or other key inputdevice that is structured to accept key press input to accept data thatis read from a magnetic stripe card by a user. For example, a magneticstripe card may include an identifier such as a PAN, that may bevisually read from the card by a user and typed into the first terminal102 via a plurality of key presses.

The first terminal 202 is communicatively coupled to a first controllercomputing device 204. In some examples, the first terminal 202 iscommunicatively coupled to the first controller computing device 204 viaa wired connection (e.g., a USB cable) or a wireless connection (e.g.,Bluetooth).

In the present example, the first controller computing device 204 isstructured as a desktop computer, smart phone, or other computingdevice. The first controller computing device 204 may be structured toinclude a computer program comprising one or more instructions that areexecutable to provide an interface to a user. The first controllercomputing device 204 may control the first terminal 202 to perform I/Ofunctions or operations. For example, the first controller computingdevice 204 may be located at a POS. In this example, the firstcontroller computing device 204 may include software, hardware, or acombination thereof that provides a purchasing interface for inputtingsales and calculating an amount due from a customer. In this example,the first controller computing device 204 is structured to communicatewith the first terminal 202 to request that the first terminal 202perform a magnetic stripe I/O operation. For example, the firstcontroller computing device 204 may activate the first terminal 202 suchthat a customer may swipe a card that includes a magnetic stripe. Thefirst terminal 202 may then read the data from the magnetic stripe, suchas a PAN, and communicate this data to the first controller computingdevice 204. In other examples, these techniques are performed in othercontexts such as authentication, ticketing, user identification, and soforth.

The system architecture 200 includes a token input device 206. In someexamples, the token input device 206 is structured as a smart card/chipcard. In other examples, the token input device 206 is structured as awireless and/or NFC-enabled device, such as a smart phone. The tokeninput device 206 is structured to generate a first token and communicatethe first token to a second terminal 208. Accordingly, in some examplesthe second terminal 208 is structured as a chip reader that reads thefirst token from the token input device 206 by communicating with amicroprocessor embedded on the smart card. In other examples, the secondterminal 208 is structured as a smart phone or other electronic devicethat reads the first token from the token input device 206 via an NFC orother wireless protocol. For example, if the token input device 206 isstructured as a smart phone or a smart card, the token input device 206may be tapped or otherwise moved within a threshold proximity to thesecond terminal 206 to allow the second terminal 208 to read the firsttoken.

The second terminal 208 is structured to communicate the first token tothe second controller computing device 210, which receives the firsttoken. In some examples, the second controller computing device 210 isstructured as hardware and/or software, such as a computer programcomprising one or more instructions that are executable to provide aninterface that controls the second terminal 208 to perform I/O functionsor operations. While in the present example the first controllercomputing device 204 and second controller computing device 210 areshown as being structured as separate computing devices, in otherexamples the first controller computing device 204 and second controllercomputing device 210 may be structured on a same computing device. Forexample, as shown in FIG. 1, a first controller and a second controllermay be structured on a client computing device. As described above withrespect to the first controller computing device 204, the secondcontroller computing device 210 may also be located at a POS.

The second controller computing device 210 may provide an interface forinputting an amount due and/or triggering the second terminal 208 toperform I/O functions or operations. In this example, the secondcontroller computing device 210 is structured to communicate to thesecond terminal 208 a request that the second terminal 208 read datafrom the token input device 206. For example, the second controllercomputing device 210 may configure and/or activate the second terminal208 such that a customer may input a first token from the token inputdevice 206 by inserting a chip card or positioning a smart phone withina threshold proximity of the second terminal 208. The second terminal208 is structured to read the first token from the smart card and/orsmart phone and communicate the first token to the second controllercomputing device 210.

The second controller computing device 210 is communicatively coupled toa network 212. The network 212 may be structured to include a privatenetwork, such as an intranet, and/or public network, such as theinternet. The second controller computing device 210 is structured totransmit data to and from the network 212 to communicate with othercomputing devices, such as one or more backend computing devices 214.

In the present example, the one or more backend computing devices 214are structured to receive and process data received from the secondcontroller computing device 210 to perform one or more transactions. Forexample, once the first controller computing device 204 receivesmagnetic stripe data from the first terminal 202, the first controllercomputing device 204 may communicate the magnetic stripe data to thenetwork 212 via a network card or other network device of the firstcontroller computing device 204. Similarly, when the second controllercomputing device 210 receives the first token from the second terminal208, the second controller computing device 210 may communicate thefirst token to the network 212 via a network card or other networkdevice of the second controller computing device 210. The network 212communicates the magnetic stripe data or first token to the one or morebackend computing devices 214 for processing. In some examples, theprocessing includes performing a transaction such as transferring fundsbetween a customer account and a merchant account. After performing thetransaction, the one or more backend computing devices 214 may notifythe first controller computing device 204 or the second controllercomputing device 210 that the transaction has been processed.

In the present example, the second terminal 208, second controllercomputing device 210, and/or one or more backend computing devices 214are structured to simulate magnetic stripe I/O by generating magneticstripe data and injecting the magnetic stripe data into the firstterminal 202 and/or first controller computing device 204. For example,this data processing may be performed as described in detail withrespect to FIG. 4. In some examples, the system architecture 200 isstructured to inject magnetic stripe data after the one or more backendcomputing devices 214 receive the first token from second controllercomputing device 210. For example, the one or more backend computingdevices 214 may generate a second token that represents a PAN or otherdata that would be read from a magnetic stripe. This second token may bestructured to include one or more digits that are uniquely identifiableas associated with the one or more backend computing devices 214. Theone or more backend computing devices 214 are then structured tocommunicate the second token to the second controller computing device210.

The second controller computing device 210 is structured to inject thePAN or other magnetic stripe data by communicating the second token tothe second terminal 208. In this example, the second terminal 208 isstructured to generate a magnetic signal to simulate a magnetic swipeoperation. The second terminal 208 communicates the second token to thefirst terminal 202 via the magnetic signal. Accordingly, the firstterminal 202 is structured to receive the second token via the magneticsignal and communicate the second token to the first controllercomputing device 204 to complete a transaction using the second token,as though the data was received from swiping a card having a magneticstripe storing the second token.

The first controller computing device 204 is structured to performtransaction processing using the second token. In some examples, thefirst controller computing device 204 is structured to transmit thesecond token to the one or more backend computing devices 214 tocomplete the transaction processing. In the present example, the secondtoken is routed to the one or more backend computing devices 214 byfirst controller computing device 204 and/or other transactionprocessing systems located on the network 212 based on recognizing thatthe second token is associated with the one or more backing computingdevices 214. As previously discussed, the second token may include anidentifier that associates the second token with the one or more backendcomputing devices 214. Accordingly, the one or more backend computingdevices 214 receive the second token as part a of a transactionprocessing operation, and may be structured to perform one or moreoperations, such as transferring funds, sending notifications to thefirst controller computing device 204, and so forth.

FIG. 3 illustrates a computer system 300 suitable for implementing oneor more computing devices. In various implementations, computer system300 may structure a computing device as a mobile phone, a computingtablet, a desktop computer, laptop, wearable device, rack mount server,or any machine capable of executing a set of instructions (sequential orotherwise) that specify actions to be taken by that machine.

Computer system 300 may include a bus 302 or other communicationmechanisms for communicating information data, signals, and informationbetween various components of computer system 300. Components include anI/O component 304 that processes a user action, such as selecting keysfrom a keypad/keyboard, selecting one or more buttons, links, actuatableelements, swiping a card via a magnetic stripe reader, tapping an NFCdevice, inputting a chip via a chip reader, etc., and sends acorresponding signal to bus 302. I/O component 304 may also include anoutput component, such as a display 306 and a cursor control 308 (suchas a keyboard, keypad, mouse, touch screen, etc.). An optional audio I/Ocomponent 310 may also be included to allow a user to hear audio and/oruse voice for inputting information by converting audio signals.

A network interface 312 transmits and receives signals between computersystem 300 and other devices, such as user devices, data servers, and/orother computing devices via a communications link 314 and a network 316(e.g., such as a LAN, WLAN, PTSN, and/or various other wired or wirelessnetworks, including telecommunications, mobile, and cellular phonenetworks).

The processor 318 represents one or more general-purpose processingdevices such as a microprocessor, central processing unit, or the like.More particularly, processor 318 may be a complex instruction setcomputing (CISC) microprocessor, reduced instruction set computing(RISC) microprocessor, very long instruction word (VLIW) microprocessor,or a processor implementing other instruction sets or processorsimplementing a combination of instruction sets. Processor 318 may alsobe one or more special-purpose processing devices such as an applicationspecific integrated circuit (ASIC), a field programmable gate array(FPGA), a digital signal processor (DSP), network processor, or thelike. Processor 318 is configured to execute instructions for performingthe operations and steps discussed herein.

Components of computer system 300 also include a main memory 320 (e.g.,read-only memory (ROM), flash memory, dynamic random access memory(DRAM) such as synchronous DRAM (SDRAM), double data rate (DDR SDRAM),or DRAM (RDRAM), and so forth), a static memory 322 (e.g., flash memory,static random access memory (SRAM), and so forth), and a data storagedevice 324 (e.g., a disk drive).

Computer system 300 performs specific operations by processor 318 andother components by executing one or more sequences of instructionscontained in main memory 320. Logic may be encoded in a computerreadable medium, which may refer to any medium that participates inproviding instructions to processor 318 for execution. Such a medium maytake many forms, including but not limited to, non-volatile media,volatile media, and/or transmission media. In various implementations,non-volatile media includes optical or magnetic disks, volatile mediaincludes dynamic memory, such as main memory 320, and transmission mediabetween the components includes coaxial cables, copper wire, and fiberoptics, including wires that comprise bus 302. In one embodiment, thelogic is encoded in a non-transitory machine-readable medium. In oneexample, transmission media may take the form of acoustic or lightwaves, such as those generated during radio wave, optical, and infrareddata communications.

Some common forms of computer readable media include, for example,floppy disk, flexible disk, hard disk, magnetic tape, any other magneticmedium. CD-ROM, any other optical medium, punch cards, paper tape, anyother physical medium with patterns of holes. RAM, PROM, EPROM,FLASH-EPROM, any other memory chip or cartridge, or any other mediumfrom which a computer is adapted to read.

In various embodiments of the present disclosure, execution ofinstruction sequences to practice the present disclosure may beperformed by computer system 300. In various other embodiments of thepresent disclosure, a plurality of computer systems 300 coupled bycommunication link 314 to the network 316 may perform instructionsequences to practice the present disclosure in coordination with oneanother. Modules described herein may be embodied in one or morecomputer readable media or be in communication with one or moreprocessors to execute or process the steps described herein.

FIG. 4 illustrates a method for processing a transaction, in accordancewith various examples of the present disclosure. In some examples, themethod 400 is implemented by one or more processors executingcomputer-readable instructions to perform the functions describedherein. It is understood that additional steps can be provided before,during, and after the steps of method 400, and that some of the stepsdescribed can be replaced or eliminated in other examples of the method400.

At action 402, a first controller receives a first token from a firstterminal. In the present example, the first terminal reads the firsttoken from a token input device, such as a smart card or smart phone. Insome examples, the token is read from an EMV-compliant chip card orEMV-compliant mobile phone using an industry standard while conducting afinancial transaction, such as a payment operation. The first terminalcommunicates the first token to the first controller via a wired and/orwireless communication medium. In some examples, the first controllerrequests that the first terminal input the first token responsive to atransaction being performed on the first controller. For example, thefirst controller may request input of the first token corresponding to apurchase of a service or good at a POS of a merchant. A pricecorresponding to the purchase may be input into the first controller,which may then trigger the first terminal to receive the first tokenfrom the token input device. In other examples, inserting a smart cardinto the first terminal, placing an NFC-capable device within athreshold proximity of the first terminal, or a user-input at the firstterminal may trigger the first terminal to read the first token andcommunicate the token to the first controller. Accordingly, the firsttoken is input at the first terminal and communicated to the firstcontroller from the first terminal. The first controller receives thefirst token from the first terminal.

In some examples, the first token includes a ciphertext that is anumeric or alphanumeric string that represents a private key and/orprimary account number (PAN) encrypted by the token input device. Forexample, the token input device may generate the first token forperforming a transaction by encrypting a private key, such as a PAN,that is associated with the token input device or a user of the tokeninput device. The first token may also be associated with a time, suchthat the first token may be invalid/expire after a threshold period oftime.

At action 404, the first controller communicates the first token via anetwork to a backend computing device, such as a transaction processingserver or other server. In some examples, the backend computing devicecomprises a plurality of computing devices. In other examples, thebackend computing device receives the first token via the network by wayof one or more other backend computing devices, such as transactionprocessing servers corresponding to a merchant.

At action 406, the backend computing device processes a transactionusing the first token. In some examples, the backend computing devicedetermines the private key, such as a PAN, corresponding to the firsttoken by decrypting the first token. The backend computing deviceperforms the transaction using the private key, such as by processing apayment corresponding to the PAN. For example, the backend computingdevice may process a transaction by transferring funds to a merchantfrom a customer account corresponding to the PAN. The backend computingdevice generates a second token as part of the transaction processingand communicates the second token to the first controller. In someexamples, the second token is generated and communicated to the firstcontroller after the transaction has been processed to transfer funds tothe merchant.

In the present example, the second token that is generated by thebackend computing device includes at least one digit that is associatedwith the backend computing device. For example, the second token mayinclude a four to six digit portion that represents a unique identifierthat is assigned to the backend computing device. These digits may beidentifiable on other computing devices, such that the other computingdevices recognize that the second token is associated with the backendcomputing device and route transactions to the backend device based onsaid recognition.

At action 408, the first controller receives the second token from thebackend computing device. After receiving the second token, the firstcontroller and/or peripheral device, such as the first terminal, injectsthe second token into a second controller. The injecting of the secondtoken into the second controller is performed to simulate I/O from amagnetic stripe or keyboard/keypad.

In some examples, the first controller injects the second token into thesecond controller by simulating a typing of the second token via aseries of key presses. For example, the first controller may call a sendkey API of the second controller's computing device to input the secondtoken into the second controller via simulated key press inputs.

In other examples, the first controller injects the second token intothe second controller by causing the first terminal or anotherperipheral device to generate a magnetic signal that simulates swiping amagnetic stripe that stores the second token. A second terminal that isstructured as a magnetic stripe card reader may read the magnetic signalto receive the second token. The second terminal may then input thesecond token into the second controller. Accordingly, magnetic stripeI/O is simulated by the first controller and/or first terminal to injectthe second token into the second controller.

At action 410, the second controller processes the second token bycommunicating the second token to the backend processing system. Forexample, the second controller may process the second token as thoughthe second token is a PAN corresponding to a credit/debit card of acustomer. Accordingly, the second controller may process a payment tothe merchant using the PAN. In some examples, the second controllermatches the one or more digits of the second token that are uniquelyidentifiable to the backend computing device to route the transaction tothe backend computing device. In other examples, the second controllerprocesses the second token by communicating the second token to apayment processor corresponding to the merchant, and the paymentprocessor matches the one or more digits of the second token to routethe second token to the backend computing device.

The backend computing device receives the second token and recognizesthe second token as generated corresponding to the processing performedat action 406. Accordingly, if the backend computing device alreadytransferred funds from the customer to the merchant after receiving thefirst token, the backend computing device may identify that the fundshave been transferred and notify the second controller that thetransaction has been processed. In other examples, the backend computingdevice may wait to transfer the funds until the second token isreceived. Accordingly, upon receiving the second token, the backendcomputing device may transfer the funds and notify the second controllerthat the transaction has been processed.

It is to be understood that the above description is intended to beillustrative, and not restrictive. Many other examples will be apparentto those of skill in the art upon reading and understanding the abovedescription. The scope of the disclosure should, therefore, bedetermined with reference to the appended claims, along with the fullscope of equivalents to which such claims are entitled.

1-20. (canceled)
 21. A system comprising: a non-transitory memory; andone or more hardware processors coupled to the non-transitory memory andconfigured to read instructions from the non-transitory memory to causethe system to perform operations comprising: receiving a first tokenread from a token input device; transmitting the first token over anetwork to at least one backend computing device; receiving, from the atleast one backend computing device, a second token that is differentthan the first token; simulating input including a magnetic stripe inputor a key press input; and providing the simulated input to a transactionprocessing device.
 22. The system of claim 21, wherein the token inputdevice comprises a chip card or a mobile phone.
 23. The system of claim21, wherein the first token is read by a chip reader device.
 24. Thesystem of claim 21, wherein the first token comprises a numeric oralphanumeric string that represents a private key or a primary accountnumber.
 25. The system of claim 21, wherein simulating the magneticstripe input includes generating a magnetic signal that transmits thesecond token to a magnetic stripe reader corresponding to thetransaction processing device.
 26. The system of claim 21, whereinsimulating the key press input includes calling an ApplicationProgramming Interface (API) function for one or more digits included inthe second token to emulate a user entering the key press input on akeyboard or a keypad device corresponding to the transaction processingdevice.
 27. The system of claim 21, wherein the first token is read viaa near-field communication (NFC) or by reading a microprocessor embeddedin a chip card.
 28. The system of claim 21, wherein the second tokenincludes an identifier portion that is uniquely identifiable to the atleast one backend computing device, and wherein the transactionprocessing device routes the second token to the at least one backendcomputing device based on the identifier portion of the second token.29. A non-transitory machine-readable medium having stored thereonmachine-readable instructions executable to cause a machine to performoperations comprising: receiving a first token read from a token inputdevice; transmitting the first token over a network to at least onebackend computing device; receiving, from the at least one backendcomputing device, a second token that is different than the first token;simulating input including a magnetic stripe input or a key press input;and providing the simulated input to a transaction processing device.30. The non-transitory machine-readable medium of claim 29, wherein thetoken input device comprises a chip card or a mobile phone.
 31. Thenon-transitory machine-readable medium of claim 29, wherein simulatingthe magnetic stripe input includes generating a magnetic signal thattransmits the second token to a magnetic stripe reader corresponding tothe transaction processing device.
 32. The non-transitorymachine-readable medium of claim 29, wherein simulating the key pressinput includes calling an Application Programming Interface (API)function for one or more digits included in the second token to emulatea user entering the key press input on a keyboard or a keypad devicecorresponding to the transaction processing device.
 33. Thenon-transitory machine-readable medium of claim 29, wherein the firsttoken is read via a near-field communication (NFC) or by reading amicroprocessor embedded in a chip card.
 34. The non-transitorymachine-readable medium of claim 29, wherein the second token includesan identifier portion that is uniquely identifiable to the at least onebackend computing device, and wherein the transaction processing deviceroutes the second token to the at least one backend computing devicebased on the identifier portion of the second token.
 35. A methodcomprising: receiving a first token read from a token input device;transmitting the first token over a network to at least one backendcomputing device; receiving, from the at least one backend computingdevice, a second token that is different than the first token;simulating input including a magnetic stripe input or a key press input;and providing the simulated input to a transaction processing device.36. The method of claim 35, wherein the token input device comprises achip card or a mobile phone.
 37. The method of claim 35, whereinsimulating the magnetic stripe input includes generating a magneticsignal that transmits the second token to a magnetic stripe readercorresponding to the transaction processing device.
 38. The method ofclaim 35, wherein simulating the key press input includes calling anApplication Programming Interface (API) function for one or more digitsincluded in the second token to emulate a user entering the key pressinput on a keyboard or a keypad device corresponding to the transactionprocessing device.
 39. The method of claim 35, wherein the first tokenis read via a near-field communication (NFC) or by reading amicroprocessor embedded in a chip card.
 40. The method of claim 35,wherein the second token includes an identifier portion that is uniquelyidentifiable to the at least one backend computing device, and whereinthe transaction processing device routes the second token to the atleast one backend computing device based on the identifier portion ofthe second token.